Skip to content

fix: resolve settings API 500 errors#915

Merged
Priyanshu-byte-coder merged 2 commits into
Priyanshu-byte-coder:mainfrom
Shravani-36:fix-settings-api-500
May 25, 2026
Merged

fix: resolve settings API 500 errors#915
Priyanshu-byte-coder merged 2 commits into
Priyanshu-byte-coder:mainfrom
Shravani-36:fix-settings-api-500

Conversation

@Shravani-36
Copy link
Copy Markdown
Contributor

@Shravani-36 Shravani-36 commented May 24, 2026

Summary

Fixed the Settings API routes that were returning 500 Internal Server Error on the deployed dashboard.

This update improves Supabase user resolution and adds safer error handling for settings-related API routes so the Settings page loads correctly.

Closes #476

Type of Change

  • Bug fix
  • New feature
  • Documentation update
  • Refactor / code cleanup

Changes Made

  • Fixed user resolution logic in resolveAppUser
  • Improved Supabase query handling for missing users
  • Added safer null/error handling in settings API routes
  • Prevented API crashes when user records are unavailable
  • Verified /dashboard/settings loads successfully locally
  • Fixed settings fetch/update response handling

How to Test

Steps for the reviewer to verify this works:

  1. Clone the repository
  2. Add valid Supabase environment variables in .env.local
  3. Run:
npm install
npm run dev
  1. Open:
http://localhost:3000/dashboard/settings

  1. Sign in with GitHub

  2. Verify:

    • Settings page loads correctly
    • Public profile toggle works
    • Leaderboard toggle works
    • Linked GitHub accounts load successfully
    • No 500 errors appear in Network tab

Screenshots (if UI change)

N/A

Checklist

  • Linked issue in summary
  • npm run lint passes locally
  • No TypeScript errors (npm run type-check)
  • Self-reviewed the diff
  • Added/updated tests if applicable

@vercel
Copy link
Copy Markdown

vercel Bot commented May 24, 2026

@Shravani-36 is attempting to deploy a commit to the PRIYANSHU DOSHI's projects Team on Vercel.

A member of the Team first needs to authorize it.

@github-actions github-actions Bot added gssoc26 GSSoC 2026 contribution type:bug GSSoC type bonus: bug fix labels May 24, 2026
@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 24, 2026

GSSoC Label Checklist 🏷️

@Priyanshu-byte-coder — please apply the appropriate labels before merging:

Difficulty (pick one):

  • level:beginner — 20 pts
  • level:intermediate — 35 pts
  • level:advanced — 55 pts
  • level:critical — 80 pts

Quality (optional):

  • quality:clean — ×1.2 multiplier
  • quality:exceptional — ×1.5 multiplier

Validation (required to score):

  • gssoc:approved — counts for points
  • gssoc:invalid / gssoc:spam / gssoc:ai-slop — does not score

Type labels (type:*) are auto-detected from files and title. Review and adjust if needed.
Points formula: (difficulty × quality_multiplier) + type_bonus

github-actions[bot]
github-actions Bot reviewed May 24, 2026
View reviewed changes
Copy link
Copy Markdown

@github-actions github-actions Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for your first PR on DevTrack! 🎉

A maintainer will review it within 48 hours. While you wait:

  • Make sure CI is passing (type-check + lint)
  • Double-check the PR description is filled out and the issue is linked
  • Feel free to ask questions in Discussions if you need help

If you find DevTrack useful, a ⭐ star on the repo is always appreciated — it helps the project grow and attract more contributors!

@Priyanshu-byte-coder Priyanshu-byte-coder added the gssoc:approved GSSoC: PR approved for scoring label May 24, 2026
@Shravani-36 Shravani-36 removed their assignment May 25, 2026
@Priyanshu-byte-coder Priyanshu-byte-coder merged commit 9c69cb5 into Priyanshu-byte-coder:main May 25, 2026
3 checks passed
@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 25, 2026

🎉 Merged! Thanks for contributing to DevTrack.

If the project has been useful to you, a ⭐ star on the repo is the easiest way to support it — it helps DevTrack get discovered by more developers.

Keep an eye on open issues for your next contribution!

Priyanshu-byte-coder added a commit that referenced this pull request May 25, 2026
@Priyanshu-byte-coder @claude
fix: resolve botched merge conflict in supabase.ts
1c755dd 
PR #915 squash-merge left branch names embedded as code artifacts
('fix-settings-api-500' and 'main') and duplicate function bodies
in getUserByUsername and updateUserPublicFlag. This caused TS errors
TS1005 and TS1472 breaking CI on main.

Clean rewrite keeps the PR #915 version (try/catch error handling,
leaderboard_opt_in in select) with no duplicate or artifact code.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@github-actions github-actions[bot] github-actions[bot] left review comments

@Priyanshu-byte-coder Priyanshu-byte-coder Awaiting requested review from Priyanshu-byte-coder Priyanshu-byte-coder is a code owner

Assignees

No one assigned

Labels

gssoc:approved GSSoC: PR approved for scoring gssoc26 GSSoC 2026 contribution type:bug GSSoC type bonus: bug fix

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

[BUG] Settings API returns 500 Internal Server Error on deployed dashboard

2 participants

@Shravani-36 @Priyanshu-byte-coder